Conversation
…n to reduce vulnerabilities The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-TARFS-10293725
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
Reviewer's GuideRemediates a high-severity tarfs vulnerability by replacing workspace references with explicit, patched versions of @backstage/backend-common and @backstage/plugin-catalog-backend in the incremental ingestion backend module’s package.json. Flow Diagram: Snyk Vulnerability Remediation Process for 'tarfs'graph TD
A["Snyk scans 'catalog-backend-module-incremental-ingestion' dependencies"] --> B{"Vulnerability found in 'tarfs'<br/>(SNYK-JS-TARFS-10293725)"};
B -- Yes --> C["'tarfs' identified as transitive dependency of:<br/>- @backstage/backend-common (via workspace:^)<br/>- @backstage/plugin-catalog-backend (via workspace:^)"];
C --> D["Snyk determines patched direct dependency versions:<br/>- @backstage/backend-common: 0.24.1<br/>- @backstage/plugin-catalog-backend: 1.25.0"];
D --> E["Snyk creates PR to update 'package.json'"];
E --> F["Change: Dependencies pinned to specific<br/>patched versions, replacing 'workspace:^'"];
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
🎉 Snyk checks have passed. No issues have been found so far.✅ security/snyk check is complete. No issues have been found. (View Details) |
| }, | ||
| "dependencies": { | ||
| "@backstage/backend-common": "workspace:^", | ||
| "@backstage/backend-common": "0.24.1", |
There was a problem hiding this comment.
This change replaces the workspace reference (workspace:^) with a fixed version number (0.24.1), which breaks the monorepo's dependency management approach. In Yarn workspaces, internal dependencies should use workspace protocol references to ensure consistent versioning across the project.
Using fixed versions instead of workspace references can lead to:
- Version mismatches between components
- Duplicate package installations
- Potential build failures
- Difficulties when updating shared dependencies
Consider maintaining the workspace:^ reference while addressing the vulnerability through other means, such as updating the yarn.lock file or using resolutions in the root package.json to pin the vulnerable transitive dependency.
| "@backstage/backend-common": "0.24.1", | |
| "@backstage/backend-common": "workspace:^", |
Spotted by Diamond
Is this helpful? React 👍 or 👎 to let us know.
|
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution! |
Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):
plugins/catalog-backend-module-incremental-ingestion/package.jsonNote for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the
.yarn/cache/directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to runyarnto update the contents of the./yarn/cachedirectory.If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:
SNYK-JS-TARFS-10293725
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Improper Link Resolution Before File Access ('Link Following')
Summary by Sourcery
Upgrade key dependencies in the incremental ingestion plugin to address a high severity tar-fs vulnerability
Bug Fixes:
Enhancements: